Sourced from @​prisma/client's releases.

5.1.0

Today, we are excited to share the 5.1.0 stable release 🎉

🌟 Help us spread the word about Prisma by starring the repo ☝️ or tweeting about the release.

Highlights

After two big releases where we released Client extensions for production usage (4.16.0) and made Prisma faster by default (5.0.0), we have focused on some smaller issues to make the experience with these new features even better.

Community contributions

Our community has been on the roll! We appreciate everyone who helps us by opening a GitHub issue or proposing a fix via Pull Requests. In this release, we're excited to highlight multiple community contributions:

• Fix IPv6 not working for relational databases: prisma/prisma-engines#4051 by @​alula
• Middlewares: Add to PrismaAction type, missing findUniqueOrThrow and findFirstOrThrow prisma/prisma#17471 by @​mejiaej and missing groupBy prisma/prisma#19985 by @​iurylippo
• Better error message in currently non-supported runtimes like Browser or Vercel Edge Runtime prisma/prisma#20163 by @​andyjy
• Remove error messages for valid NixOS setups prisma/prisma#20138 by @​Gerschtli

Better performance: Fewer SQL queries on PostgreSQL & CockroachDB

In our continued and ongoing work to make Prisma faster, we identified some Prisma Client queries that led to multiple SQL statements being executed — although in specific databases, that was not necessary.

Hence we optimized our internal SQL generation for PostgreSQL and CockroachDB to generate more efficient SQL queries:

Simple create query

In a simple create query, RETURNING makes the second query and the transaction statements obsolete:

Prisma Client query

prisma.user.create({ 
  data: { name: "Original name" } 
})

Before v5.1.0

BEGIN
INSERT INTO "User" ("name") VALUES ($1) RETURNING "User"."id"
SELECT "User"."id", "User"."name" FROM "User" WHERE "User"."id" = $1;
COMMIT

5.1.0 and later

-- Sends 1 statement (instead of 2) and omits the transaction
INSERT INTO "User" ("name") VALUES ($1) RETURNING "User"."id", "User"."name"
</tr></table> 

... (truncated)

• 0eb32dc feat(client): allow extension to reference their $parent (#20425)
• 22011ad chore(deps): update engines to 5.1.0-28.a9b7003df90aa623086e4d6f4e43c72468e63...
• 47b3ce6 fix(client): add extra schema search location (#20447)
• 8e02861 chore(deps): update dependency @​swc/jest to v0.2.27 (#20389)
• 551db6c fix(client): confusing get result types (#20435)
• b7ed20d fix(client): enum types (#20446)
• b15ac85 fix(client): Ensure result extensions are applied after all query extensions ...
• 612138c test(client): add generator-config-types test (#20118)
• 7854a5f chore(deps): update engines to 5.1.0-22.4b132e0d5319952d155d8bbe2ba802464ebf8...
• ec07b49 fix(client): types oom and inferred length errors (#20161)
• Additional commits viewable in compare view

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually